Game system including third party input

ABSTRACT

Methods, systems, devices, and media for controlling a network game in accordance with an input of a game spectator are provided. A network interface receives player input information from a game player and spectator input information from the game spectator. The network game is progressed in accordance with the player input information received by the network interface from the game player, and an aspect of the network game of the game player is controlled in accordance with the spectator input information received by the network interface. The spectator input information specifies the game player and the aspect of the network game of the game player to be controlled.

BACKGROUND

1. Field of the Disclosure

The present disclosure generally relates to the field of network gaming.More particularly, the present disclosure relates to various systems,methods, and media for controlling a network game in accordance with aninput of a game spectator.

2. Background Information

Recently, electronic gaming has become accepted as a new variety ofsport or, more appropriately, an e-sport. The acceptance of gaming as ane-sport has given rise to increasingly larger and more popular gamingevents, such as the Evolution Championship Series. These events havecreated a significant viewing interest in network gaming.

In order to satisfy the viewing interest, electronic game players haveresorted to gamecasting. Gamecasting is an activity during which a gameplayer broadcasts a live stream of his or her own game screen, typicallyusing a screen capture application. The live stream is broadcast via theInternet or other network to enable third parties to view or watch theplayer's game play during real-time.

While traditional methods of gamecasting have provided a medium forviewing electronic gaming, the third parties are typically limited toviewing only those game screens which are broadcast by the players. Inaddition, the third parties lack interactivity and involvement in thegamecasts. As such, new and improved methods for viewing network gamesare desired.

SUMMARY OF THE DISCLOSURE

The present disclosure, through one or more of its various aspects,embodiments, and/or specific features or sub-components, provides, interalia, various systems, servers, methods, media, and programs forcontrolling a network game in accordance with an input of a gamespectator.

According to a non-limiting embodiment of the present disclosure, asystem for controlling a network game in accordance with an input of agame spectator is provided. The system includes a network interface thatreceives player input information from a game player and spectator inputinformation from the game spectator. The system also includes aprocessor and a memory that includes a game program including a set ofinstructions that, when executed by the processor, causes the processorto perform operations. The operations include progressing the networkgame in accordance with the player input information received by thenetwork interface from the game player, and controlling an aspect of thenetwork game of the game player in accordance with the spectator inputinformation received by the network interface. The spectator inputinformation specifies the game player and the aspect of the network gameof the game player to be controlled.

According to one aspect of the present disclosure, the game playerexecutes a game client that establishes a connection with the gamesystem for transmitting the player input information to the networkinterface, and the game spectator does not execute the game client.

According to another aspect of the present disclosure, the networkinterface receives the spectator input information from the gamespectator via a web server. The web server provides a broadcast of thenetwork game to the game spectator.

According to yet another aspect of the present disclosure, the gamesystem further includes a broadcaster that transmits the broadcast ofthe network game to the web server.

According to still another aspect of the present disclosure, the gamesystem further includes: a game server that includes the networkinterface, the processor, and the memory; a rendering server thatreceives game information from the game server, generates a player gamescreen for the game player, and generates a spectator game screen forthe game spectator. The player game screen is transmitted to the gameplayer for display by the game player. The spectator game screen istransmitted to the broadcaster for transmission to the web server as thebroadcast of the network game.

According to an additional aspect of the present disclosure, thespectator game screen comprises the player game screen.

According to another aspect of the present disclosure, the game server,the rendering server, and the broadcaster do not transmit any game datato the game spectator.

According to yet another aspect of the present disclosure, thebroadcaster transmits identification information to the web server inassociation with the broadcast of the network game for identifying thegame player. The network interface receives the identificationinformation from the web server in association with the spectator inputinformation. The processor determines the game player from among aplurality of game players based on the identification information.

According to still another aspect of the present disclosure, the webserver provides the broadcast of the network game to the game spectatoras a unicast transmission.

According to an additional aspect of the present disclosure, thespectator input information specifies a player character of the gameplayer, and the processor controls an aspect of the player character inthe network game.

According to another aspect of the present disclosure, the aspect of theplayer character includes at least one of a hit point of the playercharacter and an item inventory.

According to yet another aspect of the present disclosure, the networkinterface is configured to receive the spectator input information at anarbitrary timing during a progress of the network game.

According to still another aspect of the present disclosure, theoperations further include transmitting a request for the spectatorinput information, with the spectator input information being receivedby the network interface in response to the request.

According to an additional aspect of the present disclosure, theprocessor controls the aspect of the network game when the networkinterface receives the spectator input information.

According to another aspect of the present disclosure, the networkinterface receives personal information of the game spectator inassociation with the spectator input information, and the processorcontrols the aspect of the network game of the game player in responseto verifying the personal information of the game spectator.

According to yet another aspect of the present disclosure, theoperations further include: transmitting an option for accepting thespectator input information to the game player based on the spectatorinput information received by the network interface; controlling theaspect of the network game of the game player in response to the gameplayer accepting the option; and penalizing the game player foraccepting the option.

According to another non-limiting embodiment of the present disclosure,a method for controlling a network game hosted by a game system inaccordance with an input of a game spectator is provided. The methodincludes the features of receiving, by a network interface, player inputinformation from a game player, and receiving, by the network interface,spectator input information from the game spectator. The method furtherincludes the features of controlling, by a processor, a progress of thenetwork game in accordance with the player input information received bythe network interface from the game player, and controlling, by theprocessor, an aspect of the network game of the game player inaccordance with the spectator input information received by the networkinterface. The spectator input information specifies the game player andthe aspect of the network game to be controlled.

According to an aspect of the present disclosure, the game playerexecutes a game client that establishes a connection with the gamesystem for transmitting the player input information to the networkinterface, and the game spectator does not execute the game client.

According to yet another non-limiting embodiment of the presentdisclosure, a non-transitory computer readable medium including aprogram for controlling a network game hosted by a game system inaccordance with an input of a game spectator is provided. The program,when executed by at least one processor of the game system, causes thegame system to perform operations including receiving, by a networkinterface, player input information from a game player, and receiving,by the network interface, spectator input information from the gamespectator. The operations further include controlling, by a processor, aprogress of the network game in accordance with the player inputinformation received by the network interface from the game player, andcontrolling, by the processor, an aspect of the network game of the gameplayer in accordance with the spectator input information received bythe network interface. The spectator input information specifies thegame player and the aspect of the network game to be controlled.

According to an aspect of the present disclosure, the game playerexecutes a game client that establishes a connection with the gamesystem for transmitting the player input information to the networkinterface, and the game spectator does not execute the game client.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is further described in the detailed descriptionwhich follows, in reference to the noted plurality of drawings, by wayof non-limiting examples of preferred embodiments of the presentdisclosure, in which like characters represent like elements throughoutthe several views of the drawings.

FIG. 1 shows an exemplary system for controlling a network game inaccordance with an input of a game spectator, according to an aspect ofthe present disclosure.

FIG. 2 shows a schematic of an exemplary game system, according to anaspect of the present disclosure.

FIG. 3 shows a further exemplary system for controlling a network gamein accordance with an input of a game spectator, according to anadditional aspect of the present disclosure.

FIG. 4 shows a block diagram of an exemplary game server, according toan aspect of the present disclosure.

FIG. 5 shows a block diagram of an exemplary rendering server, accordingto an aspect of the present disclosure.

FIG. 6 shows a flowchart of an exemplary network game process, accordingto an aspect of the present disclosure.

FIG. 7 shows a schematic of an exemplary system for controlling anetwork game in accordance with an input of a game spectator, accordingto an aspect of the present disclosure.

FIG. 8 shows a flowchart of an exemplary game process for creating adummy player for generating a spectator game scream, according to anaspect of the present disclosure.

FIG. 9 shows a flowchart of an exemplary game process for generating andtransmitting a request for spectator input information, according to anaspect of the present disclosure

FIG. 10 illustrates an exemplary display screen for controlling anetwork game in accordance with an input of a game spectator, accordingto an aspect of the present disclosure.

FIG. 11 shows an exemplary method of a game server of a network gamesystem for controlling a network game in accordance with an input of agame spectator, according to an aspect of the present disclosure.

FIG. 12 shows an exemplary method of a rendering server of a networkgame system for controlling a network game in accordance with an inputof a game spectator, according to an aspect of the present disclosure.

FIG. 13 shows an exemplary method of a broadcaster of a network gamesystem for controlling a network game in accordance with an input of agame spectator, according to an aspect of the present disclosure.

FIG. 14 shows an exemplary method of a display interface of a networkgame system for controlling a network game in accordance with an inputof a game spectator, according to an aspect of the present disclosure.

DETAILED DESCRIPTION

The present disclosure provides various network game systems, devices,methods, media, and programs for controlling a network game inaccordance with an input of a game spectator.

An exemplary embodiment of a network game system is generally shown inFIG. 1 at 100. The network game system 100 includes a game system 102 towhich a game player 104 is connected via a network 106. The game system102 receives player input information from the game player 104 andprogresses the network game in accordance with the player inputinformation. The game system 102 also receives spectator inputinformation based on an input of a game spectator 108 and controls anaspect of the network game of the game player 104 in accordance with thespectator input information. The spectator input information specifiesthe game player 104, or a game character controlled thereby, and theaspect of the network game to be controlled. For example, the spectatorinput information may increase a hit point of the player character inthe network game, add an item to an inventory of the player character,or make the player character invisible.

In an embodiment of the network game system 100, the game system 102 maygenerate and transmit a broadcast of the network game to a web server110. The broadcast may be generated and transmitted in correspondencewith a specific client view of the game player 104. The web server 110displays the broadcast, such as via a website or other displayinterface. The game spectator 108 is able to view the broadcast of thenetwork game via the web server 110, and is able to transmit thespectator input information to the game system 102, such as via the webserver 110, based on a viewing of the broadcast. Thereafter, the gamesystem 102 is able to control the aspect of the network game of the gameplayer 104, such as by associating the spectator input information withthe broadcast which is generated and transmitted in correspondence withthe specific client view of the game player 104. Since the game system102 provides the broadcast of the network game, the game system 102 isable to receive the spectator input information in associationtherewith.

Accordingly, the game spectator 108 is able to assist, hinder, orotherwise affect or control an aspect of the network game of the gameplayer 104, or a game character controlled thereby. As a result, thegame spectator 108 is provided with a sense of interactivity andinvolvement in the network game, thereby providing a more enjoyable andappealing network game viewing experience.

In addition, since the broadcast is generated by the game server 102 andprovided to the web server 110, the game spectator 108 is able to followthe broadcast of the network game without knowing, being associatedwith, or following any particular game player 104. The game spectator108 also need not possess, own, or run a network game client or othersoftware for participating in the network game, as the game spectator108 is able to access the broadcast via the web server 110. Accordingly,a broader audience of the game spectator 108 is possible.

Moreover, again since the broadcast is generated by the game system 102instead of the game player 104, the broadcast is not limited tocomprising only a view or broadcast of a screen of the game player 104.For example, the broadcast may include a specific request for thespectator input information, as well as additional game informationregarding the game player 104 or a state of the network game. Theseadditional pieces of information are not feasible with traditional,player-side broadcasting applications. In other words, the server-sidebroadcast of the present disclosure may include information which is notreadily apparent to player-side broadcasting applications. As a result,a more diverse game viewing environment is possible.

The broadcast may also include, for example, inputs andinput-combinations of the game player 104 such that the broadcast mayfunction as a teaching or learning application while still providing theinteractivity and involvement in the network game to the game spectator108. As a result, an interest in the broadcast may further be enhancedby the dual functionality of learning and control.

Still further, again since the broadcast is generated by the game system102 instead of the game player 104, the broadcast is not limited by anygraphics processing or display capabilities of the game player 104, butrather, may be provided to the web server 110 in accordance with thecapabilities of the game system 102. As a result, an improved viewingexperience is also provided.

Of course, the above-described features and advantages are not limitingor exhaustive. Additional features and advantages of the network gamesystem 100 will be apparent from the following description andembodiments. Accordingly, in view of the foregoing, the presentdisclosure, through one or more of its various aspects, embodiments,and/or specific features or sub-components, is thus intended to bringout one or more of the advantages as specifically discussed above and asnoted below.

An exemplary embodiment of the game system 102 is generally shown at 200in FIG. 2. The exemplary game system 200 of FIG. 2 is hereinafterreferred to as computer system 200 for convenience. The computer system200 may include a set of instructions that can be executed to cause thecomputer system 200 to perform any one or more of the methods orcomputer based functions disclosed herein. The computer system 200 mayoperate as a standalone device or may be connected, for example, using anetwork 202, to other computer systems or peripheral devices such as thegame player 104, the web server 110, and the game spectator 108.

In a networked deployment, the computer system 200 may operate in thecapacity of a server or as a client user computer in a server-clientuser network environment, a client user computer in cloud computingenvironment, or as a peer computer system in a peer-to-peer (ordistributed) network environment. The computer system 200 can also beimplemented as or incorporated into various devices, such as astationary computer, a mobile computer, a personal computer (PC), alaptop computer, a tablet computer, a wireless smart phone, a set-topbox (STB), a personal digital assistant (PDA), a global positioningsatellite (GPS) device, a communications device, a control system, acamera, a web appliance, a network router, switch or bridge, or anyother machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. Forexample, the computer system 200 may be implemented as, or incorporatedinto, an automobile or a wearable device, such as, but not limited to,watches, glasses, bracelets, and headsets. The computer system 200 canbe incorporated as or in a particular device that in turn is in anintegrated system that includes additional devices. In a particularembodiment, the computer system 200 can be implemented using electronicdevices that provide voice, video or data communication. Further, whilea single computer system 200 is illustrated, the term “system” shallalso be taken throughout the present disclosure to include anycollection of systems or sub-systems that individually or jointlyexecute a set, or multiple sets, of instructions to perform one or morecomputer functions.

As illustrated in FIG. 2, the computer system 200 includes a processor204. The processor 204 is tangible and non-transitory. As used herein,the term “non-transitory” is to be interpreted not as an eternalcharacteristic of a state, but as a characteristic of a state that willlast for a period of time. The term “non-transitory” specificallydisavows fleeting characteristics such as characteristics of aparticular carrier wave or signal or other forms that exist onlytransitorily in any place at any time. The processor 204 is an articleof manufacture and/or a machine component. The processor 204 isconfigured to execute software instructions in order to performfunctions as described in the various embodiments herein. The processor204 may be a general purpose processor or may be part of an applicationspecific integrated circuit (ASIC). The processor 204 may also be amicroprocessor, a microcomputer, a processor chip, a controller, amicrocontroller, a digital signal processor (DSP), a state machine, or aprogrammable logic device. The processor 204 may also be a logicalcircuit, including a programmable gate array (PGA) such as a fieldprogrammable gate array (FPGA), or another type of circuit that includesdiscrete gate and/or transistor logic. The processor 204 may be acentral processing unit (CPU), a graphics processing unit (GPU), orboth. Additionally, any processor described herein may include multipleprocessors, parallel processors, or both. Multiple processors may beincluded in, or coupled to, a single device or multiple devices.

Moreover, the computer system 200 includes at least one of a main memory206 and a static memory 208. The main memory 206 and the static memory208 can communicate with each other via a bus 210. Memories describedherein are tangible storage mediums that can store data and executableinstructions, and are non-transitory during the time instructions arestored therein. Again, as used herein, the term “non-transitory” is tobe interpreted not as an eternal characteristic of a state, but as acharacteristic of a state that will last for a period of time. The term“non-transitory” specifically disavows fleeting characteristics such ascharacteristics of a particular carrier wave or signal or other formsthat exist only transitorily in any place at any time. The memories arean article of manufacture and/or machine component. Memories describedherein are computer-readable mediums from which data and executableinstructions can be read by a computer. Memories as described herein maybe random access memory (RAM), read only memory (ROM), flash memory,electrically programmable read only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), registers, a hard disk,a removable disk, tape, compact disk read only memory (CD-ROM), digitalversatile disk (DVD), floppy disk, blu-ray disk, or any other form ofstorage medium known in the art. Memories may be volatile ornon-volatile, secure and/or encrypted, unsecure and/or unencrypted.

As shown, the computer system 200 may further include a video displaydevice 212, such as a liquid crystal display (LCD), an organic lightemitting diode (OLED), a flat panel display, a solid state display, or acathode ray tube (CRT). The video display device 212 may be integratedwith or physically separate from the components of the computer system200 described herein.

Additionally, the computer system 200 may include an input device 214,such as a keyboard/virtual keyboard or touch-sensitive input screen orspeech input with speech recognition. The computer system 200 may alsoinclude a cursor control device 216, such as a mouse or touch-sensitiveinput screen or pad, a microphone, etc. The computer system 200 may alsoinclude a signal generation device 218, such as a speaker or remotecontrol, a game disk drive unit 220, and a network interface device 222.

In a particular embodiment, as depicted in FIG. 2, the game disk driveunit 220 may include a game computer-readable medium 224 in which one ormore sets of instructions 226, e.g. software, can be embedded.Additionally or alternatively to the game disk drive unit 220, thecomputer system 200 may comprise any additional storage unit, such as,but not limited to, a solid state storage or other persistent storage,which comprises the computer-readable medium 224. Sets of instructions226 can be read from the game computer-readable medium 224. Further, theinstructions 226, when executed by a processor, can be used to performone or more of the methods and processes as described herein. In aparticular embodiment, the instructions 226 may reside completely, or atleast partially, within the main memory 206, the static memory 208,and/or within the processor 204 during execution by the computer system200.

FIG. 3 shows a further embodiment of the network game system 100 ofFIG. 1. The network game system of FIG. 3 is generally shown at 300. Inthe network game system 300 of FIG. 3, the game system 102 includes agame server 302, a rendering server 304, and a broadcaster 306. The gamesystem 102 may additionally include the network interface 110, or anycombination of the above-described entities or features as discussedwith respect to FIG. 2. The game system 102 is generally describedhereinafter as corresponding to the embodiment shown in FIG. 3.Nevertheless, it should be understood that the game system 102 mayinclude additional or alternative embodiments in accordance with theembodiment shown in FIG. 2.

The network 106 may be, but is not limited to, a local area network, awide area network, the Internet, a telephony network, or any othernetwork commonly known and understood in the art. The network 106 isshown in FIG. 3 as being a wireless network. However, those skilled inthe art appreciate that the network 106 may additionally oralternatively comprise a wired network.

The game system 102 is generally described herein as providing orhosting a network game. In this regard, the network game may be amultiplayer type network game or a single player type network game. Thenetwork game may be an action game, a shooter game, an adventure game, arole-playing game, a simulation game, a strategy game, or any other typeof game generally known and understood in the art. While the game system102 is generally described as providing the network game, additional oralternative services may also be provided without departing from thescope of the present disclosure. For example, the network game may beany other service which is provided via a network such as, but notlimited to, a music program, an art program, an animation program, etc.

The game player 104 and the game spectator 108 are each shown in FIG. 3in singular form. Nevertheless, it is to be known and understood thatthe network game system 300 may comprise a plurality of game players anda plurality of game spectators. In this regard, the game player 104 andthe game spectator 108 are generally described hereinafter in singularforms for convenience, although those of ordinary skill in the artappreciate that the plural forms may generally be used interchangeably.Also, while the game player 104 and game spectator 108, or game players104 and game spectators 108, are described as being “players” and“spectators,” it should be appreciated that the game player 104 and gamespectator 108 are not limited to being individuals but may refer to agame client, apparatus, or device, in singular and plural forms. Thegame player 104 and game spectator 108 may each be any entity or devicewhich connects with the game server 102 or the web server 110 via thenetwork 106. For example, the game player 104 and game spectator 108 mayeach be the same or similar to the computer system 200 of FIG. 2,including similar elements and features or combinations thereof.

The game server 302, the rendering server 304, and the broadcaster 306of the game system 102 may be disparate structures which are directly orindirectly connected via any of the networks described herein. In thisregard, the structures may be physical, tangible structures. Anycombination of these structures may be integral or non-integral with oneanother. They may also comprise non-tangible structures in furtherembodiments of the present disclosure. For example, the broadcaster 306may be implemented via software and included within either of the gameserver 302, the rendering server 304, or a combination thereof.

The game server 302 executes and manages a game processing program forprogressing the network game, instructs the rendering server 304 toperform an image rendering process, requests the spectator inputinformation, and exchanges game data with the game player 104. In otherwords, the game server 302 executes and manages game processing of thenetwork in which the game player 104 participates and the game spectator108 spectates. For example, the game server 302 manages game informationsuch as a position and direction on a map of a character, or characters,operated by the game player 104, and an event, or events, to be providedfor each character. The game information may include characterinformation which reflects a current status of the game player 104 orcharacter controlled thereby. The game information may also includeprogress information which reflects a current status of the network gameor service. The game server 302 also manages the player inputinformation and the spectator input information for controlling thenetwork game. The game information, including the player inputinformation and the spectator input information, may comprise or relateto any information which is understood to be associated with a networkgame or other service.

The game server 302 exchanges the game information with the renderingserver 304 and causes the rendering server 304 to generate a player gamescreen for the game player 104. For example, when the player inputinformation is received by the game server 302 from the game player 104via the network 106 as a result of an operation input of the game player104 or when the spectator input information is received from the webserver 110 via the network 106, the game server 302 executes a processof reflecting these pieces of information on the character informationof any character or characters of the game player 104 and on theenvironmental and other information of the network game. Then, the gameserver 302 determines at least one rendering object to be rendered onthe player game screen based on the information of the network game, andtransmits a rendering instruction to the rendering server 304.

The rendering server 304 renders the player game screen in accordancewith the rendering instruction received from the game server 302, andoutputs the generated player game screen directly to the game player 104or indirectly to the game player 104 via the game server 302. Therendering server 304 can simultaneously form player game screens formultiple game players 104. Alternatively, the rendering server 304 cansequentially form player game screens multiple game players 104. Ofcourse, the rendering server 304 may also perform any combination ofsimultaneously and sequentially forming player game screens.

The rendering server 304 executes a game screen rendering process by agraphics processing unit based on information received from the gameserver 302 for the player game screen. The rendering server 304 mayexecute the game screen rendering process based on identificationinformation of rendering objects contained in the player game screen,and detailed information indicating data necessary to render eachrendering object. The detailed information necessary to render eachrendering object may include, but is not limited to, informationindicating the following attribute data: identification information forspecifying model data; identification information for specifying texturedata; specific information of a rendering program, for example, ashader, to be used; and specific information of data for calculations,for example, the light source intensity, light source vector, androtation matrix, to be used in the rendering program. The detailedinformation including the above-listed information may be transmittedfrom the game server 302 to the rendering server 304, but information tobe contained in the detailed information is not limited to the aboveinformation. For example, the detailed information may contain any ofthe above-listed information, and may additionally or alternativelycontain any information to be used in the process of rendering arendering object as generally understood in the art.

The player game screen, which is rendered by the rendering server 304 inaccordance with the transmitted rendering instruction including therendering object identification information and detailed information, istransmitted to the game player 104. The game player 104 may directlyreceive the player game screen from the rendering server 304, or thegame player 104 may indirectly receive the player game screen from therendering server 304 such as by way of the game server 302 or by anyother entity. Thus, the game system 102 of FIG. 2 can generate theplayer game screen corresponding to operation input caused on a clientdevice, and provide the player game screen to the game player 104 viathe network 106. As a result, any graphic processing capabilities orrequirements of the game player 104 for participating in the networkgame may be minimized or eliminated altogether.

In addition to rendering the player game screen, the rendering server304 may also render a spectator game screen, which is included within abroadcast of the network game and viewable by the game spectator 108.The game server 302 similarly exchanges game information with therendering server 304 for causing the rendering server 304 to render thespectator game screen. The rendering server 304 generally renders thespectator game screen in a same or similar manner as the player gamescreen. Exemplary embodiments by which the rendering server 304 rendersthe spectator game screen are discussed in detail below. As analternative to rendering the spectator game screen, the game server 302,the rendering server 304, or a combination thereof may utilize theplayer game screen as the spectator game screen.

The game system 102 of FIG. 3 is shown as including one game server 302and one rendering server 304. Nevertheless, those of ordinary skill inthe art will appreciate that the present disclosure is not limited tothis arrangement. For example, it is also possible to allocate onerendering server 304 to a plurality of game servers 302, or to allocatea plurality of rendering servers 304 to a plurality of game servers 302.In further embodiments, the game system 102 may include separaterendering servers 304 for rendering the player game screen and forrendering the spectator game screen. Any rendering servers 304 may bespecifically associated with any game server 302 or any game screen.Additionally or alternatively, the game server 302 may designate arendering server 304 or a graphics processing unit of a rendering server304 to be used to execute a rendering instruction, in accordance withinformation indicating a number of game screens to be simultaneously orsequentially generated by a rendering server 304 or graphics processingunit of a rendering server 304.

The spectator game screen is transmitted directly or indirectly to thebroadcaster 306 from the rendering server 304. The broadcaster 306receives and transmits the spectator game screen to the web server 110.The broadcaster 306 may process, encode, compress, and/or output theinformation to the web server 110 in accordance any known formats and/orteachings commonly understood in the art. In this regard, any output ofthe broadcaster 306 may only be limited by the graphic processingcapabilities of the rendering server 304, as well as possibly beingrestricted by any downstream limitations of the web server 110, gamespectator 108, or network 106. Nevertheless, the output of thebroadcaster 306 may be independent of any processing and displaycapabilities of the game player 104.

The web server 110 receives the output of the broadcaster 306 and isaccessible by the game spectator 108. The web server 110 may comprise aserver, platform, application, website, or any other interface which isconfigured to process, decode, and/or broadcast images or video streamsvia a public, private, or other medium. The web server 110 may also beconfigured to receive inputs from the game spectator 108 and to transmitthe inputs to the game server 302.

Exemplary embodiments of the components of the game system 102 of FIG. 3are described below with respect to FIGS. 3-5.

FIG. 4 is a block diagram showing an exemplary functional arrangement ofthe game server 302 according to an embodiment of the presentdisclosure. The game server 302 may be, for example, a game serversystem as generally shown at 400 in FIG. 4. However, it is to beappreciated that the game server 302 may also be the same or similar tothe computer system 200 of FIG. 2. The game server 302 may comprise anycombination of the components of the computer system 200 and the gameserver system 400.

A game CPU 402 controls the operation of each block of the game serversystem 400. More specifically, the game CPU 402 reads out a gameprocessing program from, for example, a game ROM 404 or game recordingmedium 406, expands the program on a game RAM 408, and executes theprogram, thereby controlling the operation of each block. The game CPU402 may be the same or similar to the processor 204 as described withrespect to FIG. 2.

The game ROM 404 may be the same or similar to the main memory 206 ofFIG. 2. For example, the game ROM 404 may be a programmable nonvolatilememory. The game ROM 404 stores the game processing program, and mayalso store other programs. The game ROM 404 also stores information suchas a constant required for the operation of each block of the gameserver 400.

The game RAM 408 may be the same or similar to the static memory 208 ofFIG. 2. For example, the game RAM 408 may be a volatile memory. The gameRAM 408 is used not only as a game processing program expansion area,but also as a storage area for temporarily storing, for example,intermediate data output during the operation of each block of the gameserver 400.

The game recording medium 406 is, for example, a recording device suchas an HDD detachable from the center server 400. The game recordingmedium 406 may be the same or similar to the disk drive unit 220 or thecomputer-readable medium 224 of FIG. 2. In this embodiment, the gamerecording medium 406 is used as, for example, a database for managingusers and client devices using the network game, and a database formanaging various kinds of information on the network game, which arerequired to generate the player game screens to be provided for eachconnected game player 104 and to generate the spectator game screen tobe provided for the game spectator 108.

A game communication unit 410 is a communication interface of the gameserver system 400. The game communication unit 410 may be the same orsimilar to the network interface device 222 of FIG. 2. The gamecommunication unit 410 exchanges data with the game player 104, therendering server 304, the broadcaster 306, and the web server 110. Thegame communication unit 410 may convert data into a data formatcomplying with any necessary or required communication specifications.

FIG. 5 is a block diagram showing an exemplary functional arrangement ofthe rendering server 304 according to an embodiment of the presentdisclosure. The rendering server 304 may be, for example, a renderingserver system as generally shown at 500 in FIG. 5. However, it is to beappreciated that the rendering server 304 may also be the same orsimilar to the computer system 200 of FIG. 2. The rendering server 304may comprise any combination of the components of the computer system200 and the rendering server system 500.

A rendering CPU 502 controls the operation of each block of therendering server system 500. More specifically, the rendering CPU 502reads out a rendering process operation program stored in a renderingROM 504 or rendering recording medium 506, expands the program on arendering RAM 508, and executes the program, thereby controlling theoperation of each block. The rendering CPU 502 may be the same orsimilar to the processor 204 as described with respect to FIG. 2.

The rendering ROM 504 may be the same or similar to the main memory 206of FIG. 2. For example, the rendering ROM 504 may be a programmablenonvolatile memory. The rendering ROM 504 stores the rendering processoperation program, other operation programs, and information such as aconstant required for the operation of each block of the renderingserver system 500.

The rendering RAM 508 may be the same or similar to the static memory208 of FIG. 2. For example, the rendering RAM 508 may be a volatilememory. The rendering RAM 508 is used not only as an operation programexpansion area, but also as a storage area for temporarily storing, forexample, intermediate data output during the operation of each block ofthe rendering server system 500.

The rendering recording medium 506 is, for example, a recording devicesuch as an HDD detachable from the rendering server system 500. Therendering recording medium 506 may be the same or similar to the diskdrive unit 220 or the computer-readable medium 224 of FIG. 2. In thisembodiment, the rendering recording medium 506 may store the followingdata to be used to generate the game player screen and the spectatorplayer screen: model data; texture data; a rendering program; and datafor calculations to be used in the rendering program. Of course, theabove-listed data is merely exemplary and not limiting or exhaustive. Inadditional embodiments, the rendering recording medium 506 may storeadditional or alternative data without departing from the scope of thepresent disclosure.

A rendering communication unit 510 is a communication interface of therendering server system 500. The rendering communication unit 510 may bethe same or similar to the network interface device 222 of FIG. 2. Therendering communication unit 510 exchanges data with another apparatus,for example, the game player 104, the rendering server 304, and thebroadcaster 306. When transmitting data, the rendering communicationunit 510 may convert the data into a data transmission format determinedwith respect to a transmission network or a transmission destinationapparatus, and transmits the data to the transmission destinationapparatus. When receiving data, the rendering communication unit 510 mayconvert received data into an arbitrary data format readable by therendering server system 500, and store the data in, for example, therendering RAM 508.

First, second, third, and fourth rendering GPUs 512, 514, 516, and 518each generate the player game screen to be provided for each game player104 or the spectator game screen to be provided for the game spectator108. Each rendering GPU 512, 514, 516, and 518 is connected to a videomemory, such as first, second, third, and fourth rendering video RAMs(VRAMs) 520, 522, 524, and 526, as a game screen rendering area. Eachrendering GPU 512, 514, 516, and 518 may also include a cache memory(not shown). When performing rendering on the connected rendering VRAM520, 522, 524, and 526, each rendering GPU 512, 514, 516, and 518expands a rendering object on the cache memory, and writes the mappedrendering object in the corresponding rendering VRAM 520, 522, 524, and526. FIG. 5 shows one video memory being connected to each graphicsprocessor. However, it is to be known and understood that the number ofvideo memories connected to the graphics processors can be any arbitrarynumber. Moreover, FIG. 5 shows the rendering server system 500 asincluding four graphics processors. However, it is also to be known andunderstood that the graphics processors can be any arbitrary number.

Each of the broadcaster 306 and the web server 110 may comprise anycombination of the components of the computer system 200, the gameserver system 400, and the rendering server system 500.

An exemplary embodiment of basic network game processing executed on thenetwork game system 300 having the arrangement of the game server 302and the rendering server 304 as described above is generally explainedwith reference to FIG. 6. The basic network game processing is generallyshown at 600 and may be implemented by the game server 302 reading acorresponding processing program and executing the processing program,as described above with respect to FIG. 4.

The network game processing 600 may be started when, for example, thenetwork game begins or the game server 302 is activated, andrepetitively executed for each frame of the network game. In the networkgame processing 600, the game server 302 and the rendering server 304are described as providing the player game screen for the game player104. However, as will be evident from the disclosure below, similarprocessing may also be executed each frame for providing the spectatorgame screen to the broadcaster 306.

In step S602, the game server 302 determines whether informationindicating an operation input caused on the game player 104, or anyadditional game players, is received and/or whether an operation inputcaused on the game spectator 108 is received. If the game server 302determines that the information indicating any of the operation inputsis received, the game server 302 advances the process to step S604. Ifnot, the game server 302 advances the process to step S606.

In step S602, the game server 302 updates game information based on theinformation indicating the operation input on the game player 104, whichis received in step S602. For example, the game server 302 determinesstate information corresponding to a character in the network game,which is an operation target of a user of a corresponding game player104. The character state information is information of the action andappearance of the character that may be changed by the user's operation,for example, the position (e.g., coordinate information) of thecharacter on the map, the gazing direction of the character, and acharacter's action. The game server 302 refers to the received operationinput information, and updates a parameter that changes by the operationinput, among parameters contained in the state information, by thereceived operation input information. Accordingly, the game server 302can reflect, in the network game, the information of the operation inputperformed by the game player 104.

In step S606, the game server 302 updates state information of arendering object as a state management target in the network game,except for the character as an operation target of the game player 104.Examples of the rendering object as a state management target in thenetwork game may be a non-player character that is not a target of auser's operation, and a background object such as a landform. Arendering object as a state management target in the network gamechanges with time or by the action of a character as a user's operationtarget. In step S606, therefore, the game server 302 updates the stateinformation of a rendering object as a state management target in thenetwork game, in accordance with the elapse of time or the characterstate information updated in step S604.

In step S608, the game server 302 specifies rendering objects containedin the player game screen provided for the game player 104. Therendering objects contained in the player game screen may include acharacter's rendering object as a user's operation target as identifiedin S604, and a rendering object as a state management target in thenetwork game as identified in S606. In other words, the game server 302selects each game player 104 presently connected to the game server 302,and reads information of a player game screen rendering range with whicheach game player 104 is associated. The information of the game screenrendering range may include, for example, camera parameterscorresponding to the player game screen.

In step S610, the game server 302 transmits, to the rendering server304, instructions to render the player game screen to be provided forthe game player 104, and causes the rendering server 304 to executerendering processing. The game server 302 may transmit instructions forall game players 104, or for less than all game players 104. Theinstructions may be simultaneously, sequentially, or seriallytransmitted. The instructions may include, for each game player 104,identification information for the game player 104, the renderingobjects contained in the player game screen, detailed information setfor each of the rendering objects contained in the player game screen,state information of each rendering object contained in the player gamescreen, and information of the rendering range and display setting ofthe player game screen.

In an embodiment of the network game processing 600 as shown in FIG. 6,at step S612, the game server 302 may determine whether a player gamescreen generated by the rendering server 304 in accordance with arendering instruction is received from the rendering server 304. If itis determined that the player game screen is received, the game server302 advances the process to step S614 and transmits the player gamescreen to the game player 104. If the player game screen is not receivedat step S612, the game server 302 waits until the player game screen isreceived. The game server 302 may wait until all of the player gamescreens are received, such that the player game screens of all gameplayers 104 are transmitted at a same time. Alternatively, the gamesever 202 may transmit each player game screen as it is received.

In an alternative embodiment of the network game processing 600 as shownin FIG. 6, the rendering server 304 may transmit the player game screento the game player 104. In this regard, the game server 302 maydetermine whether the player game screen has been transmitted at stepS616. For example, the game server 302 may determine whether the playergame screen has been transmitted by receiving a confirmation from therendering server 304. In even further embodiments of the presentdisclosure in which the rendering server 304 transmits the player gamescreen to the game player 104, the game server 302 does not receive anyconfirmation and the network game processing 600 may end after stepS610. In accordance with the above embodiments, the rendering server 304may also transmit player game screens to all game players 104 at a sametime or as the player game screens are rendered.

The network game processing 600 of FIG. 6 is merely an exemplary methodof a configuration of the game server 302 and the rendering server 304.Additional and alternative embodiments of the network game processing600 may be provided without departing from the scope of the presentdisclosure. The shown embodiment is merely exemplary and should not beconsidered limiting.

FIG. 7 shows a schematic of the network game system 300 of FIG. 3 at700. The game server 302 includes at least one memory, such as thememories 206, 208, 224 of FIG. 2 or the memories 404, 406, 408 of FIG.4, which includes a game program including a set of instructions. Thegame program is configured to be executed by at least one processor,such as the processor 204 of FIG. 2 or the CPU 402 of FIG. 4, forperforming operations in accordance with any of the features describedherein. The game server 302 transmits and receives information amongstthe entities shown in FIG. 7 for performing the operations describedherein and progressing the network game. The game server 302 maytransmit and receive the information via a network interface, such asthe network interface device 222 of FIG. 2 or the communication unit 410of FIG. 4. The game player 104 is connected to the game server 302 forparticipating in the network game.

The game server 302 receives player input information 702 from the gameplayer 104, updates the game information based on the player inputinformation 702, and issues a rendering instruction 704 to the renderingserver 304 as generally discussed above.

The rendering instruction 704 may comprise an instruction to render asingle player game screen for the game player 104, or the renderinginstruction 704 may comprise an instruction to render multiple gamescreens for multiple players. In this regard, the rendering server 304may render a different game screen for each of the multiple players.Alternatively, the rendering server 304 may render a same game screenfor the multiple players. For example, when the network game includes agroup of characters which cooperate as a party, the rendering server 304may render a same game screen for the players which control thecharacters of the party. In any event, the rendering server 304 isconfigured to render the player game screen for the game player 104, orfor multiple game players 104, based on the rendering instruction 704received from the game server 302.

The rendering server 304 receives the rendering instruction 704,including the necessary game information, from the game server 302 andgenerates the player game screen. The player game screen is transmittedto the game player 104 as video information 706 for display by the gameplayer 104. In the embodiment shown in FIG. 7, the rendering server 304provides the video information 706 directly to the game player 104. Therendering server 304 may transmit the video information 706 to the gameplayer 104 via the network 106 (not shown). The video information 706may be transmitted to the game player 104 as a unicast transmission orcommunication. The game server 302 may separately provide audioinformation 708 to the game player 104. The game server 302 may alsotransmit the audio information 708 to the game player 104 via thenetwork 106 (not shown). The audio information 708 may also betransmitted to the game player 104 as a unicast transmission orcommunication. Of course, those of ordinary skill in the art appreciatethat, in alternative embodiments of the present disclosure as generallydiscussed with respect to FIG. 6, the rendering server 304 may providethe video information 706 to the game server 302, whereupon the gameserver 302 provides the video information 706 and the audio information708 to the game player 104.

The rendering instruction 704 provided by the game server 302 to therendering server 304 may further include an instruction for generatingor rendering a spectator game screen. The spectator game screen isgenerated or rendered such that the game spectator 108 may watch or viewthe network game without participating therein. While the game player104 participates in the network game and may control a player characterof the network game, the game spectator 108 does not participate in thenetwork game and may not control any player character of the networkgame. In this regard, the game spectator 108 is not connected to thegame server 302 or the game system 102, and the game spectator 108 doesnot receive any game information directly from the game server 302, therendering server 304, or the game system 102.

While the game player 104 includes or executes a game client forparticipating in the network game, the game spectator 108 does notinclude or execute the game client. The game client may be any piece ofsoftware which connects to the game system 102 for participating in thenetwork game. The game client may facilitate or comprise an interfacefor exchanging information between the game player 104 and the gamesystem 102, including the game server 302 and the rendering server 304.The game client may, for example, facilitate the exchange of the playerinput information 702, the video information 706, the audio information708, and/or any additional game data. The game client may be stored orinstalled by the game player 104. For example, the game client may beincluded within any combination of the main memory 206, static memory208, drive unit 220, and computer readable medium 226 as described withrespect to FIG. 2. The game client may additionally or alternatively beaccessed remotely by the game player 104. For example, the game clientmay be accessed by the game player 104 via the network 106 (not shown)and stored in a cloud computing system or managed by the game system102. In these embodiments, the game player 104 may access a website forexecuting the game client. Of course, the above description is merelyexemplary and the game client may comprise any additional or alternativeembodiments or features as understood in the art. In any event,information of the network game is accessible to the game player 104 viathe game client, whereas information of the network game, including thespectator game screen, may only be accessible to the game spectator 108via the web server 110 or an alternative distribution mechanism as thegame spectator 108 does not include or execute the game client. As aresult, the game spectator 108 need not obtain, own, or access the gameclient for viewing the network game.

The spectator game screen may be managed by the game server 302 andcontrolled via the rendering instruction 704. In an embodiment of thepresent disclosure, the game server 302 may manage the spectator gamescreen by executing a game process as generally shown at 800 in FIG. 8.That is, a spectator game screen management process may be initializedat step S802. The process may be initialized when the network game isinitiated, when game play is started, or when the game server 302 isactivated. After initialization, the game server 302 may determinewhether a spectator mode of the network game is enabled at step S804. Ifthe spectator mode is enabled, the game server 302 may create a dummyplayer or fake client which is not controlled by any game player 104 atstep S806. The game server 302 may create and manage the dummy player ina database in a same or similar manner as the game player 104. Aftercreation of the dummy player at step S806, game processing of thenetwork game is resumed at step S808 in accordance with normal gameprocessing, for example, as described with respect to FIG. 6.

According to the spectator game screen management process 800 of FIG. 8,the game server 302 manages the spectator game screen as correspondingto the dummy player. As a result, the game server 302 may transmit asimilar, or same, rendering instruction 704 to the rendering server 304for generating the spectator game screen in correspondence with thedummy player as if transmitting the rendering instruction 704 to therendering server 304 for generating the player game screen of the gameplayer 104. In other words, the rendering instruction 704 for generatingthe spectator game screen need not be distinguishable, different, orseparate from the rendering instruction 704 for generating the playergame screen. Thus, any physical structure or functionality of therendering server 304 need not be altered or modified for generating thespectator game screen.

The game server 302 may create the dummy player at step S806 incorrespondence with a fixed reference point in the network game. Thatis, the game server 302 may create the dummy player as having a fixedposition (e.g., coordinate information) on a game map or in a game spaceor environment. The game server 302 may additionally or alternativelycreate the dummy player as having a fixed gazing direction or viewingangle.

In further embodiments of the present disclosure, the game server 302may create the dummy player as having a fixed position (e.g., coordinateinformation) on the game map or in the game space or game environment,while having a variable gazing direction or viewing angle. The variableviewing angle or direction may be configured in accordance with apredetermined pattern or based on predetermined rules. For example, thepredetermined pattern may be set to continuously pan the game space orgame environment from a left-to-right direction, or vice-versa, in asweeping manner. The predetermined rules may be set, for example, suchthat the viewing angle or direction follows a closest character or awinning character. The predetermined rules may additionally oralternatively be set based on a priority of events in the network game.For example, viewing a battle may take precedence over viewing aconversation. Of course, the above examples are merely exemplary and arenot limiting or exhaustive.

In even further embodiments of the present disclosure, the game server302 may create the dummy player as having a variable position (e.g.,coordinate information) on the game map or in the game space or gameenvironment, while having either a fixed or variable gazing direction orviewing angle. The variable position of the dummy character may beconfigured to move throughout the game space or the game environment inaccordance with a predetermined pattern or in association withpredetermined events or conditions. The predetermined pattern may berepetitive or arbitrary to enhance variety and spectator interest. Thepredetermined events or conditions may include being offset apredetermined distance from a position of the game player 104 or anyadditional player, such as a winning player. The predetermined events orconditions may also include events in the network game, such as battlesor conversations. In this regard, the dummy character may be configuredto follow the events based on priority. For example, the dummy charactermay be configured to follow battle events in priority to conversations.Once again, those of ordinary skill in the art will appreciate that theabove examples are exemplary and are not limiting or exhaustive. In suchembodiments in which the position of the dummy character is variable,the game program may cause the game server 302 to receive the movementsof the dummy character as the player input information 702 pursuant tostep S602 of the game processing 600 of FIG. 6. As a result, the gameserver 302 may update the character state information of the dummycharacter at step S604 in similarity with updates to the character stateinformation of the game player 104.

In additional embodiments of the present disclosure, the game server 302may create the dummy player at step S806 in correspondence with ananimate or inanimate object of the network game. For example, the gameserver 302 may create the dummy player in correspondence with a sun,moon, star, or bell tower. According to such an embodiment, thespectator game screen, as viewed by the dummy player, may be provided asan overhead view of the game space or game environment without requiringadditional computations for determining a position of the dummy player.The game server 302 may further create the dummy player incorrespondence with an object in the network game, such as an enemycharacter or animal. By this means, the spectator game screen may bemoved within the game space or game environment while minimizingcomputations and maintaining a natural look and feel of the networkgame. An interest of the game spectator 108 will also be enhanced byproviding a feeling of participation within the network game. Onceagain, the above examples are merely exemplary and are not limiting orexhaustive. In accordance with these embodiments, the game program maycause the game server 302 to receive information of the animate orinanimate objects as the player input information 702 pursuant to stepS602 of the game processing 600 of FIG. 6. Alternatively, the gameserver 302 may replicate or copy the state information of the animate orinanimate objects from processing performed pursuant to step S606 of thegame processing 600 of FIG. 6.

In the above-described exemplary and non-limiting embodiments, thespectator game screen is generally managed by the game server 302 so asto be different than the player game screen of the game player 104. Thespectator game screen may comprise a global view of the network game,and thus, the game spectator 108 need not specifically follow or haveloyalty to the game player 104. Thus, diversity and breadth of the gamespectator 108 may be increased.

Nevertheless, the spectator game screen may also be the same or includea specific client view or the player game screen of the game player 104.According to such embodiments, the game server 302 may configure thedummy player to be the same as or similar to the game player 104. Inthis regard, the game program may cause the game server 302 to receivethe player input information 702 of the game player 104 as the playerinput information 702 of the dummy player at S602 of the game processing600 of FIG. 6. For example, the game program may store identificationinformation of the game player 104 as identification information of thedummy player. When the player input information 702 is received whichincludes the identification information, the player input information702 may be associated with the game player 104 and also with the dummyplayer, with the character state information of each of the game player104 and the dummy player being updated in step S604. As a result,redundant rendering instructions 704 may be transmitted for generatingeach of the player game screen of the one of the game player 104 and thespectator game screen of the game spectator 108 at S610. Accordingly,the structure or functionality of the rendering server 304 need not bemodified for accommodating the spectator game screen.

Alternatively, a same rendering instruction 704 may be transmitted forgenerating both the player game screen of the game player 104 and thespectator game screen of the game spectator 108 at S610. The renderingserver 304 may generate a single game screen as both the player gamescreen of the game player 104 and the spectator game screen of the gamespectator 108. According to such an embodiment, a processing load on thegame server 302 may be reduced via duplication.

In the embodiments of the present disclosure in which the dummy playeris configured to be the same or similar to the game player 104, thedummy player may be fixed to the game player 104 for a duration of thenetwork game. In this regard, the game player 104 may be selected fromamong other players based on a ranking of the game player 104, a statusor role of the game player 104 in the network game, a selection by thegame spectator 108, or based on any other criteria which is known andunderstood in the art.

The dummy player need not, however, be fixed to the game player 104 foran entire duration of the network game. That is, a configuration of thedummy player may switch between different players, or between any of theother configurations of the dummy player described herein. For example,the rendering server 304 may generate the spectator game screen incorrespondence with the game player 104 for a number of frames followedby a different player for a number of frames. The game server 302 mayeven create and manage multiple dummy players for generating multiplescreens corresponding to multiple players at a same time. Accordingly,the broadcast of the network game, which comprises the spectator gamescreen, may stream views of multiple players simultaneously,consecutively, sequentially, serially, or otherwise. According to suchembodiments, the game spectator 108 may watch or view multiple players,thereby creating further appeal and interest.

While the spectator game screen has been described above as being basedon the creation and management of the dummy player, it should beunderstood that the spectator game screen may alternatively be orcomprise any one or combination of the player game screens which aretransmitted to the game players 104. In other words, the spectator gamescreen may comprise any one or combination of specific game playerviews. In this regard, the game server 302 need not create and managethe dummy character. Instead, any one or combination of the specificgame player views which is generated by the rendering server 304 mayalso be the spectator game screen.

The rendering server 304 transmits the generated spectator game screento the broadcaster 306 as rendering server broadcast information 710.The broadcaster 306 receives the rendering server broadcast information710, processes, encodes, and/or compresses the information, andtransmits the resultant data to the web server 110 as broadcastinformation 712. The broadcast information 712 may include only therendering server broadcast information 710 received from the renderingserver 304. Alternatively, the broadcaster 306 may also receive gameserver broadcast information 714 transmitted to the broadcaster 306 fromthe game server 302. The game server broadcast information 714 mayinclude, for example, audio information of the network game. In thisregard, the broadcaster 306 may receive video information from therendering server 304 as the rendering server broadcast information 710,and receive audio information from the game server 302 as the gameserver broadcast information 714. The broadcaster 306 may merge thevideo information and the audio information in accordance with any knownand understood methods or protocols. For example, the broadcaster 306may merge the video information and the audio information in accordancewith real time messaging protocol (RTMP), and transmit the resultantaudio and visual stream to the web server 110 as the broadcastinformation 712. The broadcast information 712 generally comprises thebroadcast of the network game.

The web server 110 receives the broadcast information 712 from thebroadcaster 306, whereupon the web server 110 provides the broadcast ofthe network game to the game spectator 108.

The web server 110 may also receive a request for spectator inputinformation which is to be displayed in connection with the broadcast.The request for the spectator input information is a request by the gamesystem 102 for input from the game spectator 108. The request may begenerated by the game server 302 and transmitted directly or indirectlyto the web server 110. For example, the request may be transmitted fromthe game server 302 to the rendering server 304 in accordance with therendering instruction 704. In this regard, the request may comprise agraphic or menu that is generated by the rendering server 304 in, or inassociation with, the spectator game screen. The request may then betransmitted from the rendering server 304 to the broadcast server 306 inaccordance with the rendering server broadcast information 710, andoutput by the broadcast server 306 to the web server 110 as thebroadcast information 712. Additionally, or alternatively, the requestfor the spectator input information may be transmitted from the gameserver 302 to the broadcast server 306 in accordance with the gameserver broadcast information 714. The broadcaster 306 may receive therequest as a content source of the broadcast information 712, or thebroadcast of the network game. The broadcaster 306 may combine orcompile the request and the rendering server broadcast information 710,and output the resultant data or stream to the web server 110 as thebroadcast information 712. In even further embodiments, the request forthe spectator input information may be transmitted directly from thegame server 302 to the web server 110 as a spectator input informationrequest 716. In any event, the web server 110 receives the request forthe spectator input information for display in association with thespectator game screen or the broadcast of the network game, such thatthe game spectator 108 may control the aspect of the network game.

The aspect of the network game which is controlled via the request mayrelate directly to the game player 104. The request may enable the gamespectator 108 to directly help, hinder, or otherwise affect the gameplayer 104, or a character controlled thereby, in the network game. Forexample, the request may enable the game spectator 108 to control astatus of the game player 104, or a character controlled thereby, in thenetwork game. The status may be controlled by, for example, raising orlowering a health or hit point or a maximum health or hit point of thegame player 104 or character controlled thereby, placing the game player104 or character controlled thereby in a predetermined state such as afrozen, invisible, fast, or slow state, or raising or lowering a levelof the game player 104 or character controlled thereby. The request mayfurther enable the game spectator 108 to control an ability of the gameplayer 104, or a character controlled thereby, in the network game. Theability may be controlled by, for example, increasing or decreasing apower of an action of the game player 104 or character controlledthereby, making available or unavailable an action to the game player104 or character controlled thereby, or making available or unavailablea turn or opportunity to the game player 104 or character controlledthereby. The request may even further enable the game spectator 108 tocontrol a knowledge or inventory of the game player 104 or charactercontrolled thereby. In this regard, the game spectator 108 may providethe game player 104 or character controlled thereby with an item, clue,map, information, or other element of the network game. Of course, theseexamples are merely exemplary and the game spectator 108 may directlycontrol an aspect of the network game of the game player 104 inaccordance with additional or alternative methods without departing fromthe scope of the present disclosure.

The aspect of the network game which is controlled via the request mayadditionally or alternatively relate indirectly to the game player 104.That is, the request may enable the game spectator 108 to indirectlyhelp, hinder, or otherwise affect the game player 104 by controlling theaspect with respect to a friend character or enemy character of the gameplayer 104. For example, when the spectator game screen corresponds to aspecific client view of the game player 104, the request may enable thespectator to affect all friend characters or enemy characters which aredisplayed within the specific client view. As a result, the gamespectator 108 may indirectly affect the game player 104 by controllingan aspect with respect to all friend or enemy characters which areviewable by the game spectator 108. This enables the spectator 108 toview the controlled aspect without affecting all characters in thenetwork game space. The aspect of the network game which is indirectlycontrolled in relation to the game player 104 may include any aspectdescribed above with respect to the game player 104 or any additionalaspect of a network game which is known and understood.

The game server 302 may execute game processing as generally shown at900 in FIG. 9 for transmitting the request for the spectator inputinformation. The game server 302 undergoes spectator requesttransmission initialization processing at step S902. The spectatorrequest transmission initialization processing step S902 may begin inaccordance with each frame, a clock-cycle, as a result of the playerinput information 702 being received by the game server 302 from thegame player 104, or based on any additional or alternative criteria. Forexample, the request for the spectator input information may begenerated in correspondence with a view to which the spectator gamescreen is switched, with a content of the request also corresponding tothe view or specific player view to which the spectator game screen isswitched or initiated. As a result, interest in viewing the network gameis preserved when the spectator game screen is switched. The spectatorrequest transmission initialization processing step S902 mayadditionally or alternatively be performed in accordance with any of theadditional features of the present disclosure, such as, but not limitedto, when the rendering instruction 704 is transmitted from the gameserver 302 to the rendering server 304.

After initialization, the game server 302 determines whether a conditionfor transmitting the request for the spectator input information issatisfied at step S904. The condition may be related to any status orstate of the network game as generally understood in the art. Forexample, the condition may be related to an event which is occurring orwill be occurring in the network game. In other words, the condition maybe related to a storyline of the network game. The condition may bepreprogrammed or predetermined. For example, the condition may besatisfied in association with a predetermined event of the network game.The condition may also include a random or variable element. Forexample, the condition may be dependent on the spectator game screen.That is, the decision as to whether to request the spectator inputinformation may depend on whether the aspect which is to be controlledis displayed by the spectator game screen. The game server 302 maydecide to request the spectator input information to determine theeffect of a relic which is discovered by a character which is displayedin the spectator game screen, but determine not to request the spectatorinput information to determine the effect of a relic which is discoveredby a character which is not visible in the spectator game screen. In anadditional example, the game server 302 may request control over anaspect of a battle which is occurring in the spectator game screen, butnot request control over an aspect of a battle which is not occurring inthe spectator game screen. According to these embodiments, spectatorcontrol may be limited to aspects which are viewed and of interest tothe game spectator 108. Of course, these examples are merely exemplaryand are not limiting or exhaustive. The game server 302 may determinewhether to request control over any aspect of the network game inaccordance with any additional conditions which are known and understoodin the art without departing from the scope of the present disclosure.

If the spectator request condition is satisfied at step S904, the gameserver 302 generates and transmits the request for the spectator inputinformation at step S906. As discussed above, the game server 302 maytransmit the request for the spectator input information to the gameserver 304, the broadcaster 306, or the broadcast interface 110. Thegame server 304 may transmit the request in accordance with any knownprocedures and protocols.

Thereafter, game processing of the network game is resumed at step S908in accordance with normal game processing, for example, as describedwith respect to FIG. 6. Additionally or alternatively, the gameprocessing may reconfigure the dummy player or the spectator game screento correspond to the request for the spectator input information, whichwas generated and transmitted by the game server 302. According to suchan embodiment, the aspect which is to be controlled by the request maybe made viewable to the game spectator 108 via the spectator gamescreen.

As discussed above, the web server 110 receives the request for thespectator input information, directly or indirectly from the game server302, together with the broadcast information 712 output by thebroadcaster 306. The web server 110 makes the request and theinformation available to the game spectator 108 as broadcast gameinformation 718 of the network game, and has a functionality ofdistributing the broadcast game information 718 to the game spectator108. The broadcast game information 718 which is made available to thegame spectator 108 includes the broadcast of the network game whichcomprises the spectator game screen, as well as the request for thespectator input information. The broadcast game information 718 may alsoinclude any additional game information described herein, such as, butnot limited to, character status information and network game stateinformation. The web server 110 may comprise a single distributioninterface, such as a website, or the web server 110 may comprisemultiple distribution interfaces which comprise a content distributionor delivery network.

In any event, in the embodiment of the disclosure shown in FIG. 7, theweb server 110 is an interface between the game system 102 and the gamespectator 108. The game server 302, the rendering server 304, and thebroadcaster 306 may not transmit any information or game data to thegame spectator 108. The game server 302, the rendering server 304, andthe broadcaster 306 also may not receive any information from the gamespectator 108, including any inputs from the game spectator 108 inresponse to the request for the spectator input information. By thismeans, the web server 110 functions as a replacement for, andalternative to, the game client. The web server 110 may execute softwareor programming for connecting to the game system 102 or game server andrelaying the spectator input information. However, the game spectator108 need not execute the game client or communicate with the game system102, including the game server 302, the rendering server 304, and thebroadcaster 306.

The web server 110 may provide the broadcast game information 718 to thegame spectator 108 via any known and understood methods. For example,the web server 110 may include a website or portal which the gamespectator 108 may access via the network 106 for viewing the broadcastgame information 718. In this regard, the web server 110 may live-streamthe broadcast game information 718. Additionally or alternatively, theweb server 110 may provide the broadcast game information 718 as adownloadable object or application. In any event, the web server 110provides a medium for broadcasting or transmitting the network game tothe game spectator 108, and may include any known content distributionnetwork, system, server, or application which provides the broadcastgame information 718 in accordance with any known protocol, format, orstandard. The broadcast game information 718 may be transmitted to thegame spectator 108 via a unicast transmission or a multicasttransmission.

An exemplary embodiment of the broadcast game information 718 is shownin FIG. 10. The broadcast game information 718 is shown as beingdisplayed on a display screen 1000 of the game spectator 108, such asthe video display device 212 as described with respect to FIG. 2. Thedisplay screen 1000 includes a broadcast 1002 of the network game,including the spectator game screen. The broadcast 1002 is shown in FIG.10 as comprising a specific client view. The specific client viewcorresponds to the player game screen of the game player 104.Nevertheless, it should be understood that the broadcast 1002 mayadditionally or alternatively comprise any of the views discussedherein.

The display screen 1000 is shown as including a game spectator inputsection 1004. The game spectator input section 1004 may include aportion which describes the request for the spectator input informationfrom the game server 302, and a portion which accepts a reply or inputfrom the game spectator 108. The portion of the game spectator inputsection 1004 which accepts the reply or input from the game spectator108 may accept a yes-or-no input, a multiple-choice input, an open-endedinput, or any other input which is known in the art. In this regard, therequest for the spectator input information may comprise a yes-or-norequest, a multiple choice request, an open-ended request, or any otherrequest which is known in the art. The game spectator input section 1004may also receive a request for personal information from the gamespectator 108. The request for personal information is described below.Of course, the display screen 1000 of FIG. 10 is merely exemplary andadditional displays are available without departing from the scope ofthe present disclosure. For example, additional embodiments of thedisplay screen 1000 may include multiple client views. In this regard,the broadcaster 306 may be configured to receive and compile multiplevideo sources for output to the web server 110 as the broadcastinformation 712, or the broadcaster 306 may be configured to receive andoutput multiple broadcasts to the web server 110. Even furtherembodiments of the display screen 1000 may include any game data whichis received by the broadcaster 306. For example, the broadcaster 306 maybe configured to receive and output menu data of the network game or theplayer input information 702 of the game player 104.

The broadcast of the network game is viewable to the game spectator 108via the display screen 1000 such that the game spectator 108 may viewthe network game, learn from the operation of the game player 104,control the aspect of the network game of the game player 104, andexperience any of the additional features and advantages describedherein. The broadcast of the network game may be freely available to thegame spectator 108, or the game spectator 108 may be required tocomplete an authentication or log-in process prior to viewing thebroadcast of the network game.

For controlling the aspect of the network game of the game player 104,the game spectator 108 transmits spectator input information 720 to theweb server 110. The spectator input information 720 is submitted inresponse to the request for the spectator input information, which isrelayed to the game spectator 108 by the web server 110. While therequest for the spectator input information has generally been describedherein as a formal request, it should be understood that the request maycomprise an opportunity or open invitation to submit the spectator inputinformation 720. In other words, the spectator input information 720need not be submitted in reply to any specific request. The spectatorinput information 720 may be submitted via a keyboard, mouse,touch-screen, controller, voice-recognition software, or any other inputdevice or means which is understood in the art.

The spectator input information 720 includes a specification of the gameplayer 104 and the aspect of the network game of the game player 104 tobe controlled. For example, the spectator input information 720 mayidentify the game player 104 and indicate to increase a hit point of aplayer character controlled thereby. The spectator input information 720may alternatively identify the game player 104 and indicate an itemwhich is to be provided to a player character controlled thereby. Thespectator input information 720 may alternatively identify the gameplayer 104 and indicate an enemy character thereof which is to befrozen. Of course, these examples are merely exemplary and the aspect ofthe network game of the game player 104 which is to be controlled mayinclude any of the embodiments described herein or which are known andunderstood in the art.

While the spectator input information 720 is described as including anidentification of the game player 104, it should be understood that thisinformation need not be provided by the game spectator 108. For example,the game server 302, rendering server 304, or broadcaster 306 maytransmit identification information to the web server 110 which isincluded in or associated with the broadcast information 712. In thisregard, when the broadcast of the network game is associated with thespecific client view, the identification information may identify thegame player 104 to which the specific client view corresponds. The webserver 110 may maintain the identification information in associationwith the broadcast of the network game, and correlate the identificationinformation with the received spectator input information 720.Accordingly, in the event that the game spectator 108 is watching abroadcast of the network game which is associated with a specific clientview or game player 104, the game spectator 108 may not be required toprovide identification information of the game player 104. That is, thegame spectator 108 may be limited to only providing the spectator inputinformation for the game player 104 to which the broadcast corresponds.Nevertheless, it should be understood that in further embodiments of thepresent disclosure, such as when the broadcast of the network gamecorresponds to a global view, the game spectator may provide theidentification information of the game player 104.

The spectator input information 720 may also include personalinformation of the game player 108. The personal information maycomprise identification or user information of the game spectator 108,payment or financial information, or any other information commonlyknown and understood in the art. The identification or user informationmay be required to prevent malicious or unwarranted inputs from the gamespectator 108. The identification or user information may also berequired to develop user interest and loyalty. For example, theidentification or user information may be associated with a ranking orlevel of the game spectator 108. The ranking or level may determine theaspects of the network game which the game spectator 108 is able tocontrol, such as the game spectator 108 may require a first ranking orlevel for controlling an aspect directly with respect to the game player104 and a second ranking or level being higher or lower than the firstranking or level for controlling an aspect with respect to friend orenemy characters of the game player 104. The ranking or level may alsodetermine a magnitude of the aspect which the game spectator 108 is ableto control. For example, a higher ranking may enable the game spectator108 to provide additional items or higher increases in status or hitpoints to the game player 104. Of course, these examples are merelyexemplary and are not exclusive or exhaustive.

The personal information may additionally or alternatively includepayment information to prevent malicious or unwarranted inputs and toalso limit a total number of inputs received by the web server 110 orthe game system 102. The payment information may require a fixed paymentamount per input, or the payment information may be a variable paymentamount depending upon a status of the network game or the nature of theaspect to be controlled. The payment amount may increase in accordancewith the examples described with respect to the ranking or level of thegame spectator 108 described in the preceding paragraph. The paymentamount may also increase during a predetermined event, such as a battle,or the payment amount may increase in accordance with a status of thegame player 104, such as a hit point of a character controlled by thegame player 104. That is, the payment amount may increase when a hitpoint of the game player 104 approaches zero or is below otherpredetermined threshold values. The payment amount may linearly increasewith the status of the game player 104, or the payment amount mayincrementally increase when the status is above or below thepredetermined threshold values. The payment amount may correspond toreal-world currency, or the payment amount may correspond to a virtualcurrency which is accumulated by participating in the network game or inanother network game hosted by the game server 102. Requiring thevirtual currency which is accumulated by participating in the networkgame would foster a sense of community amongst the game players 104 ofthe network game, whereupon the game players 104 may reciprocally assistone another in the network game by being game spectators 108.

Upon receipt of the spectator input information 720 from the gamespectator 108, the spectator input information 720 is transmitted fromthe web server 110 to the game server 302, or the game system 102. Inthis regard, the spectator information 702 may be configured to bereceived by the web server 110 from the game spectator 108 ortransmitted from the web server 110 to the game server 302 at apredetermined timing or at an arbitrary timing during a progress of thenetwork game. That is, the request for the spectator input informationmay be valid for a predetermined time period or set to expire at aspecific timing. The spectator input information 720 may be received bythe web server 110 during the time period or before the expiration ofthe specific timing. The spectator input information 720 may betransmitted from the web server 110 to the game server 302 upon theexpiration of the time period or at the specific timing. By this means,a plurality of game spectators 108 may provide the spectator inputinformation with equal opportunity, or the spectator input informationmay be set to be received for a predetermined event or timing in thenetwork game. Any timing for providing the spectator input informationmay be provided to or hidden from the game spectator 108.

Alternatively to the above, the spectator input information 720 may beconfigured to be received by the web server 110 from the game spectator108 or transmitted from the web server 110 to the game server 302 at anarbitrary timing during a progress of the network game. In other words,the game spectator 108 may provide the spectator input information atany timing during the network game. For example, the game spectator 108may be provided with a fixed or constant request for providing the gameplayer 104 with a healing portion or for increasing a status of the gameplayer 104 during the network game, whereupon the game spectator 108 mayprovide the healing portion or increase the status of the game player104 at any time during the network game. Additionally or alternatively,a request to provide the game player 104 an item or game information maybe constantly issued during the network game, whereupon the gamespectator 108 may elect to provide the game player 104 with the item orthe game information at any time during the network game. The item orthe game information may be constant throughout the game, or the item orthe game information may be variable. For example, the item or the gameinformation may change upon being provided to the game player 104, inaccordance with a scenario of the network game, or based upon anexpiration of a specific time period.

The web server 110 receives the spectator input information 720 from thegame spectator 108 and transmits the spectator input information 720 tothe game server 302, or the game system 102, as spectator inputinformation 722. In this regard, the web server 110 may determinewhether an input condition is satisfied before transmitting thespectator input information 722 to the game server 302. For example, theweb server 110 may verify or authenticate any personal information,including the identification or user information or the payment orfinancial information, of the spectator input information 720 beforetransmitting the spectator input information 722. Alternatively, the webserver 110 may transmit the spectator input information 722 upon theexpiration of a predetermined time period or a specific timing of therequest. In any event, the web server 110 transmits the spectator inputinformation 720 to the game server 302 as the spectator inputinformation 722, such that the game server 302 may control the aspect ofthe network game of the game player 104 in accordance with the spectatorinput information 722.

The game server 302, or the game system 102, receives the spectatorinput information 722 from the web server 110 and determines the gameplayer 104 and the aspect of the network game of the game player 104 tobe controlled therefrom. The game server 302 may immediately control theaspect of the network game of the game player 104 upon receipt of thespectator input information 722. Since the aspect is controlled inreal-time, the aspect of the game which is controlled may comprise alatent feature of the network game. This may enhance the viewingopportunity of the game spectator 108 by providing immediategratification for any spectator input information 720.

Alternatively to the above, the game server 302 may await expiration ofany of the above-discussed time periods or timing before executing thespectator input information 722. Additionally or alternatively, the gameserver 302 may provide the game player 104 with an option of acceptingthe spectator input information 722 and having the aspect of the networkgame controlled in accordance with a reply to the option. The gameserver 302 may transmit the option to the game player 104 based on thespectator input information 722 received from the web server 110, andcontrol the aspect of the network game of the game player 104 inresponse to the game player 104 accepting the option. The option may beprovided to the game player 104 solely for confirming that the gameplayer 104 desires the aspect to be controlled accordingly.Alternatively, the game player 104 may be penalized for accepting theoption. For example, if the aspect of the network game which is to becontrolled includes adding an item to an inventory of the game player104, the penalty may include a reduction in a hit point of the gameplayer 104. A status of the game player 104 in the network game may benegatively or adversely be affected by the penalty, or a general statusof the game player 104 may be affected with respect to, but not in, thenetwork game. For example, a ranking or level of the game player 104 maybe adversely affected by accepting the option. According to suchembodiments, the game player 104 is able to weight any benefits ofaccepting the spectator input information 722 with the penalty.

Accordingly, as generally shown in FIG. 7, the game server 302 requeststhat the game spectator 108 control an aspect of the network game of thegame player 108. The request is transmitted directly or indirectly fromthe game server 302 to the web server 110. The web server 110 displaysthe request together with a broadcast of the network game, which may bea specific client view of the game player 104. The web server 110receives the spectator input information 720 from the game spectator108, and transmits the spectator input information 722 to the gameserver 302. The game server 302 controls the aspect of the network gameof the game player 104 in accordance with the spectator inputinformation 722, possibly depending on whether the game player 104accepts an option for accepting the spectator input information 722.According to such embodiments, the game server 302 does not transmit anygame information to the game spectator 108. The game server 302 alsodoes not receive any input from the game spectator 108, but rather,receives the spectator input information 722 from the web server 110.

While FIG. 7 shows the broadcast of the network game, including therequest for the spectator input information, as being provided via theweb server 110, it should be understand that the broadcast and therequest may be provided directly to the game spectator 108 from the gamesystem 102 in additional embodiments of the present disclosure. Forexample, the broadcast and the request may be transmitted to the gamespectator 108 from the broadcaster 306. In this regard, the gamespectator 108 may provide the spectator input information 720 directlyto the game server 302, or to the game system 102. It should evenfurther be understood that the rendering server 304 may provide thespectator game screen to the game spectator 108 in lieu of the broadcastof the network game. In such embodiments, the rendering server 304 orthe game server 302 may provide the request for the spectator inputinformation to the game spectator 108, whereupon the game spectator 108provides the spectator input information 720 directly to the game server302, or to the game system 102. In such embodiments, the game spectator108 may be required to execute the game client for communicating withthe game system 102.

According to further embodiments of the present disclosure, as shown byFIGS. 11-14, various methods for controlling a network game inaccordance with an input of a game spectator are provided. The methodsmay be computer-implemented or implemented in accordance with any otherknown hardware or software which is capable of executing a set ofinstructions, steps, or features, sequentially or otherwise.

FIG. 11 shows an exemplary method of the game server 302 of FIG. 7. Themethod is generally shown at 1100. The game server 302 executes a gameprogram at step S1102. The game server 302 may execute the game program,for example, when the network game begins, when the game server 302 isactivated, or when the player input information 702 is received from thegame player 104. The game server 302 manages game player information atstep S1404. The game server 302 may create or update the game playerinformation in accordance with the game process 600 of FIG. 6, or inaccordance with any of the other embodiments described herein. The gameserver 302 may also manage dummy player information at step S1106. Thegame server 302 may create the dummy player information in accordancewith the game process 800 of FIG. 8, and update the dummy playerinformation in accordance with the game process 600 of FIG. 6. The gameserver 302 generates and transmits the rendering instruction 704,including game information on a progress of the network game, to therendering server 304 at step S1108. The game information may include themanaged game player information, the managed dummy player information,and/or any additional information. The game server 302 transmits networkgame information to the game players at step S1110, and transmits thespectator input information request 716 to the web server 110 at stepS1112. The network game information which is transmitted to the gameplayer 104 at step S1110 may include, for example, the audio information708 as described with respect to FIG. 7. Moreover, the network gameinformation may also be transmitted to the game broadcaster 306 duringstep S1110. Thereafter, player input information is received from thegame player 104 at step S1114, and spectator input information isreceived from the web server 110 at step S1116. The player inputinformation may include, for example, the player input information 702as described with respect to FIG. 7. The spectator input information mayinclude, for example, the spectator input information 722 as describedwith respect to FIG. 7. The game server 302 progresses the network gamein accordance with the player input information at step S1118, and alsocontrols an aspect of the network game of the game player 104 inaccordance with the spectator input information at step S1120. Theprocessing may thereafter be ended or resumed at step S1102 inaccordance with, for example, each frame of the network game. Of course,the method of FIG. 11 is merely exemplary and may additionally oralternatively include any of the features described with respect to thegame server 302 herein.

FIG. 12 shows an exemplary method of the rendering server 304 of FIG. 7.The method is generally shown at 1200. The rendering server 304 receivesthe rendering instruction 704, including the game information, at stepS1202. The request for the spectator input information may further bereceived at step S1202 in additional embodiments of the presentdisclosure. The rendering server 304 generates a player game screen atstep S1204, and generates a spectator game screen at step S1206. Therendering server 304 may generate the player game screen and thespectator game screen in accordance with any of the embodimentsdescribed herein. The rendering server 304 transmits the player gamescreen to the game player 104 at step S1208, and transmits the spectatorgame screen to the broadcaster 306 at step S1210. The request for thespectator input information may also be transmitted to the broadcasterat step S1210. Thereafter, processing may end or be restarted. Theprocessing may, for example, be executed each frame of the network game.Of course, the method of FIG. 12 is merely exemplary and mayadditionally or alternatively include any of the features described withrespect to the rendering server 304 herein.

FIG. 13 shows an exemplary method of the broadcaster 306 of FIG. 7. Themethod is generally shown at 1300. The broadcaster 306 may initially beconfigured to define a broadcast stream layout including any combinationof audio, data, and video sources at step S1302. The broadcaster 306receives network game information from the game server 302 at stepS1304, and receives network game information from the rendering server304 at step S1304. The network game information which is received fromthe game server 302 at step S1304 may include, for example, the gameserver broadcast information 714 as described with respect to FIG. 7 andalso the request for the spectator input information. The network gameinformation which is received from the rendering server 304 at stepS1306 may include, for example, the rendering server broadcastinformation 710 as described with respect to FIG. 7. The broadcaster 306compiles the network game information received from the game server 302and the rendering server 304 at step S1308, and transmits a broadcast ofthe network game, such as the broadcast information 712 as describedwith respect to FIG. 7, to the web server 110 at step S1310. Thereafter,processing may end or be restarted. The processing may, for example, beexecuted each frame of the network game. Of course, the method of FIG.13 is merely exemplary and may additionally or alternatively include anyof the features described with respect to the broadcaster 306 herein.

FIG. 14 shows an exemplary method of the web server 110 of FIG. 7. Themethod is generally shown at 1400. The web server 110 receives thebroadcast of the network game, including the spectator game screen, fromthe broadcaster 306 at step S1402 and receives the request for spectatorinput information directly or indirectly from the server 302 at stepS1404. The web server 110 displays the broadcast and the request at stepS1406, and receives spectator input information from the game spectator108 in response to the request at step S1408. Thereafter, the web server110 may determine whether an input condition for the spectator inputinformation is satisfied at step S1410. Upon determining that the inputcondition is satisfied, the web server 110 transmits the spectator inputinformation to the game server 302 at step S1414. Thereafter, processingmay end or be restarted. The processing may, for example, be executedeach frame of the network game. Of course, the method of FIG. 14 ismerely exemplary and may additionally or alternatively include any ofthe features described with respect to the web server 110 herein.

Although systems, methods, and media for broadcasting a network game toa game spectator have been described with reference to several exemplaryembodiments, it is understood that the words that have been used arewords of description and illustration, rather than words of limitation.Changes may be made within the purview of the appended claims, aspresently stated and as amended, without departing from the scope andspirit of the systems, methods, and media for broadcasting a networkgame to a game spectator in their aspects.

Although systems, methods, and media for broadcasting a network game toa game spectator have been described with reference to particular means,materials and embodiments, the systems, methods, and media are notintended to be limited to the particulars disclosed; rather the systems,methods, and media for broadcasting a network game to a game spectatorextend to all functionally equivalent structures, methods, and uses suchas are within the scope of the appended claims.

While the computer-readable medium is shown to be a single medium, theterm “computer-readable medium” includes a single medium or multiplemedia, such as a centralized or distributed database, and/or associatedcaches and servers that store one or more sets of instructions. The term“computer-readable medium” shall also include any medium that is capableof storing, encoding or carrying a set of instructions for execution bya processor or that cause a computer system to perform any one or moreof the methods or operations disclosed herein.

In a particular non-limiting, exemplary embodiment, thecomputer-readable medium can include a solid-state memory such as amemory card or other package that houses one or more non-volatileread-only memories. Further, the computer-readable medium can be arandom access memory or other volatile re-writable memory. Additionally,the computer-readable medium can include a magneto-optical or opticalmedium, such as a disk or tapes or other storage device to capturecarrier wave signals such as a signal communicated over a transmissionmedium. Accordingly, the disclosure is considered to include anycomputer-readable medium or other equivalents and successor media, inwhich data or instructions may be stored.

Although the present specification describes components and functionsthat may be implemented in particular embodiments with reference toparticular standards and protocols, the disclosure is not limited tosuch standards and protocols. Such standards are periodically supersededby more efficient equivalents having essentially the same functions.Accordingly, replacement standards and protocols having the same orsimilar functions are considered equivalents thereof.

The illustrations of the embodiments described herein are intended toprovide a general understanding of the structure of the variousembodiments. The illustrations are not intended to serve as a completedescription of all of the elements and features of the disclosuredescribed herein. Many other embodiments may be apparent to those ofskill in the art upon reviewing the disclosure. Other embodiments may beutilized and derived from the disclosure, such that structural andlogical substitutions and changes may be made without departing from thescope of the disclosure. Additionally, the illustrations are merelyrepresentational and may not be drawn to scale. Certain proportionswithin the illustrations may be exaggerated, while other proportions maybe minimized. Accordingly, the disclosure and the figures are to beregarded as illustrative rather than restrictive.

One or more embodiments of the disclosure may be referred to herein,individually and/or collectively, by the term “invention” merely forconvenience and without intending to voluntarily limit the scope of thisapplication to any particular invention or inventive concept. Moreover,although specific embodiments have been illustrated and describedherein, it should be appreciated that any subsequent arrangementdesigned to achieve the same or similar purpose may be substituted forthe specific embodiments shown. This disclosure is intended to cover anyand all subsequent adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the description.

Methods described herein are illustrative examples, and as such are notintended to require or imply that any particular process of anyembodiment be performed in the order presented. Words such as“thereafter,” “then,” “next,” etc. are not intended to limit the orderof the processes, and these words are instead used to guide the readerthrough the description of the methods. Further, any reference to claimelements in the singular, for example, using the articles “a,” “an,”“the,” etc. is not to be construed as limiting the element to thesingular.

The Abstract of the Disclosure is provided to comply with 37 C.F.R.§1.72(b) and is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, various features may begrouped together or described in a single embodiment for the purpose ofstreamlining the disclosure. This disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter may be directed toless than all of the features of any of the disclosed embodiments. Thus,the following claims are incorporated into the Detailed Description,with each claim standing on its own as defining separately claimedsubject matter.

The preceding description of the disclosed embodiments is provided toenable any person skilled in the art to make or use the presentdisclosure. As such, the above disclosed subject matter is to beconsidered illustrative, and not restrictive, and the appended claimsare intended to cover all such modifications, enhancements, and otherembodiments which fall within the true spirit and scope of the presentdisclosure. Thus, to the maximum extent allowed by law, the scope of thepresent disclosure is to be determined by the broadest permissibleinterpretation of the following claims and their equivalents, and shallnot be restricted or limited by the foregoing detailed description.

What is claimed is:
 1. A game system for controlling a network game inaccordance with an input of a game spectator, the game systemcomprising: a network interface that receives player input informationfrom a game player, spectator input information from the game spectator,and personal information of the game spectator in association with thespectator input information; a processor; and a memory that includes agame program including a set of instructions that, when executed by theprocessor, causes the processor to perform operations including:progressing the network game in accordance with the player inputinformation received by the network interface from the game player;transmitting an option for accepting the spectator input information tothe game player based on the spectator input information received by thenetwork interface; controlling an aspect of the network game of the gameplayer in accordance with the spectator input information received bythe network interface in response to verifying the personal informationof the game spectator and the game player accepting the option; andpenalizing the game player for accepting the option, wherein thespectator input information specifies the game player and the aspect ofthe network game of the game player to be controlled.
 2. The game systemaccording to claim 1, wherein the game player executes a game clientthat establishes a connection with the game system for transmitting theplayer input information to the network interface, and the gamespectator does not execute the game client.
 3. The game system accordingto claim 2, wherein the network interface receives the spectator inputinformation from the game spectator via a web server, the web serverproviding a broadcast of the network game to the game spectator.
 4. Thegame system according to claim 3, further comprising: a broadcaster thattransmits the broadcast of the network game to the web server.
 5. Thegame system according to claim 4, further comprising: a game server thatincludes the network interface, the processor, and the memory; and arendering server that receives game information from the game server,generates a player game screen for the game player, and generates aspectator game screen for the game spectator, wherein the player gamescreen is transmitted to the game player for display by the game player,and the spectator game screen is transmitted to the broadcaster fortransmission to the web server as the broadcast of the network game. 6.The game system according to claim 5, wherein the spectator game screencomprises the player game screen.
 7. The game system according to claim5, wherein the game server, the rendering server, and the broadcaster donot transmit any game data to the game spectator.
 8. The game systemaccording to claim 4, wherein the broadcaster transmits identificationinformation to the web server in association with the broadcast of thenetwork game for identifying the game player, the network interfacereceives the identification information from the web server inassociation with the spectator input information, and the processordetermines the game player from among a plurality of game players basedon the identification information.
 9. The game system according to claim4, wherein the web server provides the broadcast of the network game tothe game spectator as a unicast transmission.
 10. The game systemaccording to claim 1, wherein the spectator input information specifiesa player character of the game player, and the processor controls anaspect of the player character in the network game.
 11. The game systemaccording to claim 10, wherein the aspect of the player characterincludes at least one of a hit point of the player character and an iteminventory.
 12. The game system according to claim 1, wherein the networkinterface is configured to receive the spectator input information at anarbitrary timing during a progress of the network game.
 13. The gamesystem according to claim 1, wherein the operations further comprise:transmitting a request for the spectator input information, wherein thespectator input information is received by the network interface inresponse to the request.
 14. The game system according to claim 1,wherein the processor controls the aspect of the network game when thenetwork interface receives the spectator input information, depending onwhether the game player accepts the option.
 15. A method for controllinga network game hosted by a game system in accordance with an input ofgame spectator, the method comprising: receiving, by a networkinterface, player input information from a game player; receiving, bythe network interface, spectator input information from the gamespectator and personal information of the game spectator in associationwith the spectator input information; controlling, by a processor, aprogress of the network game in accordance with the player inputinformation received by the network interface from the game player;transmitting an option for accepting the spectator input information tothe game player based on the spectator input information received by thenetwork interface; controlling, by the processor, an aspect of thenetwork game of the game player in accordance with the spectator inputinformation received by the network interface in response to verifyingthe personal information of the game spectator and the game playeraccepting the option; and penalizing the game player for accepting theoption, wherein the spectator input information specifies the gameplayer and the aspect of the network game to be controlled.
 16. Themethod according to claim 15, wherein the game player executes a gameclient that establishes a connection with the game system fortransmitting the player input information to the network interface, andthe game spectator does not execute the game client.
 17. Anon-transitory computer-readable medium including a program forcontrolling a network game hosted by a game system in accordance with aninput of a game spectator, the program, when executed by at least oneprocessor of the game system, causing the game system to performoperations comprising: receiving, by a network interface, player inputinformation from a game player; receiving, by the network interface,spectator input information from the game spectator and personalinformation of the game spectator in association with the spectatorinput information; controlling, by a processor, a progress of thenetwork game in accordance with the player input information received bythe network interface from the game player; transmitting an option foraccepting the spectator input information to the game player based onthe spectator input information received by the network interface;controlling, by the processor, an aspect of the network game of the gameplayer in accordance with the spectator input information received bythe network interface in response to verifying the personal informationof the game spectator and the game player accepting the option; andpenalizing the game player for accepting the option, wherein thespectator input information specifies the game player and the aspect ofthe network game to be controlled.
 18. The non-transitorycomputer-readable medium according to claim 17, the operations furthercomprising: the game player executes a game client that establishes aconnection with the game system for transmitting the player inputinformation to the network interface, and the game spectator does notexecute the game client.